The suggested plugin is no longer maintained.

Could you give some context to this statement? I could not find anything supporting that claim.

@eps1lon Check npm last publish.

@eps1lon Check npm last publish.

Which is 0.3. Neither 0.3 nor https://www.npmjs.com/package/babel-plugin-react-remove-properties/ are marked as deprecated. Could you be more specific why you think that package is no longer maintained?

Which is 0.3. Neither 0.3 nor https://www.npmjs.com/package/babel-plugin-react-remove-properties/ are marked as deprecated. Could you be more specific why you think that package is no longer maintained?

I meant the last publish date which is March 2019!
I didn't say it's deprecated. It just could be a little bit frightening to use a plugin that hasn't been updated for 2 years!

Also supporting active packages is encouraging for their maintainers. That's just my opinion!

It just could be a little bit frightening to use a plugin that hasn't been updated for 2 years!

It didn't need one for over 2 years. That's a good sign. I looked at the repo and it has a single open issue. No open PRs. That's one of the cleanest states I've seen a repo in that didn't have an update in 2 years.

Also supporting active packages is encouraging for their maintainers.

It also encourages maintainers to constantly re-publish their package just to stay relevant. Let's relieve maintainers of some pressure. I'm just speaking for myself here but I'm no looking forward to having all my packages replaced just because I didn't update needlessly.

I meant the last publish date which is March 2019!
I didn't say it's deprecated.

"no longer maintained" and "deprecated" are very close concepts but I understand that this was putting words in your mouth. Still, not having received an update is not sufficient evidence that it's no longer maintained. Especially if said package didn't need maintenance. And I work with the author on other projects so I know he's still active.

It didn't need one for over 2 years. That's a good sign. I looked at the repo and it has a single open issue. No open PRs. That's one of the cleanest states I've seen a repo in that didn't have an update in 2 years.

That's right.

Especially if said package didn't need maintenance. And I work with the author on other projects so I know he's still active.

Cool, I didn't know that.
I re-wrote branch history and removed the plugin commit.

This is a good fix, but we should probably rename the commit on merge

@nickmccurdy Could you clarify why this is a good fix in your opinion in light of my comments in this conversation?

Nevermind, the PR was changed.

@ErfanMirzapour Thanks!